chore(agents): refresh the dogfood AGENTS.md and pin it to the packaged block - #2290
chore(agents): refresh the dogfood AGENTS.md and pin it to the packaged block#2290PathGao wants to merge 1 commit into
Conversation
…ed block The repo's own AGENTS.md had drifted to an older revision of the always-on block — it still told agents to read GRAPH_REPORT.md first, while graphify/always_on/agents-md.md (what install writes for users) moved to query-first rules and the wiki soft-guard long ago. Refresh it by applying the real splice, and add a test that runs _replace_or_append_section against the checked-in file and requires a no-op, so a packaged-block edit forces the dogfood copy along in the same change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![graphify-labs[bot]](https://avatars.githubusercontent.com/in/4356270?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify review — findings
This PR updates the repo's AGENTS.md graphify section, rewriting the rules to emphasize a query-first workflow (graphify query/path/explain) and adding guidance about the /graphify command and handling dirty graph files. It also adds a new test (tests/test_always_on_dogfood.py) that runs the real install splice logic against the repo's own AGENTS.md and asserts it matches the packaged graphify/always_on/agents-md.md block. The intent is to keep the dogfooded AGENTS.md in sync with the packaged block that gets installed for users.
No blocking issues surfaced. 1 lower-confidence candidate did not survive cross-model review.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 5 functions depend on the 5 node(s) this change touches.
Health — grade A; no new coupling hotspots.
Verification — 5 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 5 function(s) in the blast radius were not formally verified this run
1 participant
Summary
The repo's own
AGENTS.mdcarried an older revision of the always-on block than whatgraphify installwrites for users fromgraphify/always_on/agents-md.md: it still told agents to readGRAPH_REPORT.mdfirst and to navigatewiki/unconditionally, while the packaged block moved to query-first rules and the "if wiki exists" soft-guard. (The unconditional wiki wording is the same surface #2006 flags.)Two changes:
AGENTS.mdis regenerated by applying the real splice (_replace_or_append_section+_always_on("agents-md")) — byte-for-byte what an install would produce.No behavior change for users — the packaged block is untouched; only the repo's own copy catches up.
🤖 Generated with Claude Code